Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1118

reference
512-tree-1
name
1118
tree-preservation-order

undefined

512-tpo-1
uprn
address-text
point
POINT (-1.021546 50.898699)
geometry
MULTIPOLYGON (((-1.021489 50.898693,-1.021492 50.898704,-1.021500 50.898714,-1.021512 50.898722,-1.021528 50.898727,-1.021545 50.898729,-1.021563 50.898727,-1.021579 50.898722,-1.021592 50.898715,-1.021600 50.898705,-1.021603 50.898694,-1.021600 50.898682,-1.021592 50.898672,-1.021580 50.898664,-1.021564 50.898659,-1.021547 50.898657,-1.021529 50.898659,-1.021513 50.898664,-1.021500 50.898672,-1.021492 50.898682,-1.021489 50.898693)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL